home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000035_sanguish@digifix.com_Fri Sep 24 23:07 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
7KB
Received: from yvax2.byu.edu by maine.et.byu.edu; Fri, 24 Sep 93 23:07:03 -0600
Return-Path: <sanguish@digifix.com>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3CDW8Z6BK94GOSM@yvax.byu.edu>; Fri, 24 Sep 1993 23:04:57 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3CDW502Z4935TVN@yvax.byu.edu>; Fri, 24 Sep 1993 23:04:51 MDT
Received: from yvax.byu.edu by alaska.et.byu.edu; Fri, 24 Sep 93 23:06:36 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3CDVTX5GW935OQH@yvax.byu.edu>; Fri, 24 Sep 1993 23:04:37 MDT
Received: from nic.hookup.net by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3CDVOF5OW94GLMW@yvax.byu.edu>; Fri, 24 Sep 1993 23:04:31 MDT
Received: from digifix.com (digifix.digifix.com [198.133.162.23]) by
nic.hookup.net (8.6.beta.12/0.4) with SMTP id BAA19850; Sat,
25 Sep 1993 01:04:19 -0400
Received: by digifix.com id AA16731 (5.65c/IDA-1.4.4 for misckit@byu.edu); Sat,
25 Sep 1993 01:04:07 -0400
Received: by NeXT.Mailer (1.95)
Received: by NeXT Mailer (1.95)
Date: Sat, 25 Sep 1993 01:04:07 -0400
From: Scott Anguish <sanguish@digifix.com>
Subject: Re: MiscKit summary and proposal: stirring up the ashes
To: yackd@alaska.et.byu.edu (Don Yacktman)
Cc: misckit@byu.edu
Reply-To: sanguish@digifix.com
Message-Id: <199309250504.AA16731@digifix.com>
Content-Transfer-Encoding: 7BIT
Status: RO
Don 'verbose' Yacktman had alot to say about the Misc kit and where he'd like to see it go from here.
I don't think there is much, if anything that I would want to raise an objection to.
(1) Prefixes...
MiscKit and Misc. Yes! This seems like an excellent prefix, and will
definately cover the kit. It seems fitting also because Don originally
called it the DAYMisckit, and although we are getting rid of the DAY part
it seems fitting that the rest stay.
(2) Licensing issues.
This is such a sniggly issue with everyone, but I agree with Don's
direction here. Just PD would mean that it may not be as well
accepted.
(3) Maintaining Source
Yes! I'm curious if there might be some incentive adopt a 'standard'
revision control system for this. Something like CVS which is designed
specifically for multiple users at different locations who may need to
be editing files at the same time.
An EXCELLENT utility contribution would be for someone to write a front
end for CVS for NEXTSTEP, then we could use it in the development of the
kit, and it could be adopted as part of the kit as well.
(4) Commercial apps using the MiscKit
Having to credit the individual contributors in a commercial
program would also have that same negative effect. However, being
required to credit the MiscKit either in the online docs, the info panel
or the printed docs seems reasonable.
Nobody should be required to distribute the MiscKit to a customer if you
use it. However it would certainly be appropriate for them to point
out how to get it, and should be allowable for them to provide it to the
customer if they want to.
(5) CDROM distributions:
(6) Third party distributions:
(7) Modified distributions must be labelled as such.
(8) People who modify the source do NOT have to send
No real problems here. I'm not sure about 7 though. Do we really want
the potential problems of people releasing modified versions of the MiscKit
and then someone trying to get an upgrade and suddenly find that there were
modifications to basic classes that we didn't adopt, or were not offered.
(9) What will be accepted into the kit?
(1) creative interface widgets, all of which should be palettized
(2) abstract things which don't need to be on a palette, but it's OK if
they are.
What about stuff like development tools that we use in the creation of
the misc kit? The proposed CVS interface, perhaps a really smart
formatted documentation generator [ :-) ]. I've also sent some stuff
to Don about some ideas for a different style of Digital Librarian. If
someone is interested in working with the Indexing Kit and can put a
solid effort into this, I'll send the specs off to them, or perhaps the
mailing list at large.
(10) For now, it will be up to a developer to ....
Yep.
But this does bring up a question... can everyone agree on the basic layout
as far as directories go?
/LocalDeveloper/Headers/misckit
/LocalDeveloper/Documentation/MiscKit
/LocalDeveloper/Source/MiscKit
/LocalDeveloper/lib
/LocalDeveloper/Palettes
are all pretty much supported by NeXT, and thats the way I have currently
organized things on my drive. I'm curious how Don has stuff organized.
Everyone??
I also suggested to Don that we try and organize individual classes under
SubProj directories that could easily be added to your own projects,
instead of just linking with a library.
In a case like the ClockView, the organization would be along the lines
of
ClockView/
-rw-r--r-- 1 sanguish wheel 235 Aug 4 10:54 ClockViewInspector.h
-rw-r--r-- 1 sanguish wheel 1495 Aug 4 11:02 ClockViewInspector.m
drwxrwxr-x 5 sanguish wheel 1024 Aug 17 16:01 English.lproj/
drwxrwxr-x 5 sanguish wheel 1024 Aug 17 16:01 SubProj.bproj/
-rw-rw-r-- 1 sanguish wheel 907 Aug 14 02:23 Makefile
-rw-r--r-- 1 sanguish wheel 217 Aug 4 15:37 Makefile.postamble
-rw-r--r-- 1 sanguish wheel 265 Aug 4 15:37 Makefile.preamble
-rw-r--r-- 1 sanguish wheel 81 Aug 2 20:31 NXClockPalette.h
-rw-r--r-- 1 sanguish wheel 69 Aug 2 20:31 NXClockPalette.m
-rw-r--r-- 1 sanguish wheel 6148 Aug 4 15:32 NXClockPalette.tiff
-rw-r--r-- 1 sanguish wheel 118 Aug 4 10:39 PB.gdbinit
-rw-rw-r-- 1 sanguish wheel 677 Aug 14 02:22 PB.project
-rw-r--r-- 1 sanguish wheel 336 Aug 2 20:40 palette.table
ClockView.bproj/
-rw-r--r-- 1 sanguish wheel 1297 Aug 14 02:16 ClockView.h
-rw-r--r-- 1 sanguish wheel 9520 Aug 17 15:57 ClockView.m
-rw-r--r-- 1 sanguish wheel 113498 Aug 14 02:19 clockstuff.tiff
-rw-r--r-- 1 sanguish wheel 118 Aug 4 10:39 PB.gdbinit
-rw-rw-r-- 1 sanguish wheel 677 Aug 14 02:22 PB.project
So that in your programs you could use the palette in IB, but you could
just add the ClockView.bproj/ in your code. That would eliminate the
Interface Builder stuff, and group the related code together.
Comments?
(11) Each contributor will be recognized with a top-level
Yes!
(12) Object "owner's" responsibilities should include the
following:
Yes!
(13) I'd like to have a file at the top level, a sort of "to-do" list
Oh yes. Actually, this is something that we should be talking
about now on the list. Even simple stuff would be useful.
(14) Backward compatibility:
yes, but in order to make this easier, if you are working on a class
perhaps you should consider putting your class design up for comment
before hand, so that others can give you input before you commit to it
and as a result commit others.
That covers about everything I can think of. So if you have any comments on that, send it to the list and/or to me.
--
- Scott Anguish -
sanguish@digifix.com (NextMail)
next-announce@digifix.com (comp.sys.next.announce submissions)